Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2caa15c5982fa4ca7e8ae1f55fc8607f60c503f3986fbefcda3c496d2961ec9

Tx prefix hash: cfc93b3c43d9cf117d694151ee193e92763bfeaac8b54cbacc50c82f1e27efed
Tx public key: 51b525a354b4d42159eed103bd7ad5fddafee7a8301fe982a4db18d5a85b8e19
Timestamp: 1704249400 Timestamp [UCT]: 2024-01-03 02:36:40 Age [y:d:h:m:s]: 01:166:23:20:44
Block: 926963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380374 RingCT/type: yes/0
Extra: 0151b525a354b4d42159eed103bd7ad5fddafee7a8301fe982a4db18d5a85b8e190211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e566569450a86211015c32b6b74f70e183f1d5c087c03e85525390b72f89810 0.600000000000 1384763 of 15

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": 926973, "vin": [ { "gen": { "height": 926963 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e566569450a86211015c32b6b74f70e183f1d5c087c03e85525390b72f89810" } } ], "extra": [ 1, 81, 181, 37, 163, 84, 180, 212, 33, 89, 238, 209, 3, 189, 122, 213, 253, 218, 254, 231, 168, 48, 31, 233, 130, 164, 219, 24, 213, 168, 91, 142, 25, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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