Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 044b5b710914c3405b0e23dc06e58f30bb9abb081fe160357c77ee8c32788df8

Tx prefix hash: f5df59930c7d6e3017d5c8f5b0bedcc3fa9763c717ef5b67f3d3c18f9d36e7d0
Tx public key: 15306552144744861303a6e883086c826d7fb5a4aa80f9a8870c838e3c759585
Timestamp: 1698965513 Timestamp [UCT]: 2023-11-02 22:51:53 Age [y:d:h:m:s]: 02:007:08:41:17
Block: 883381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524835 RingCT/type: yes/0
Extra: 0115306552144744861303a6e883086c826d7fb5a4aa80f9a8870c838e3c75958502110000000a33af99f4000000000000000000

1 output(s) for total of 0.726092659000 dcy

stealth address amount amount idx
00: 1015ada03344d945b14bde04a3eac0fb39e8553d68df939dc1f3fe7094d6629d 0.726092659000 1339075 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 883391, "vin": [ { "gen": { "height": 883381 } } ], "vout": [ { "amount": 726092659, "target": { "key": "1015ada03344d945b14bde04a3eac0fb39e8553d68df939dc1f3fe7094d6629d" } } ], "extra": [ 1, 21, 48, 101, 82, 20, 71, 68, 134, 19, 3, 166, 232, 131, 8, 108, 130, 109, 127, 181, 164, 170, 128, 249, 168, 135, 12, 131, 142, 60, 117, 149, 133, 2, 17, 0, 0, 0, 10, 51, 175, 153, 244, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8