Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d779f7953ee09ae3f30b4ed3afe35fd394287ce13a908bfdf9452ceec7928835

Tx prefix hash: 26977ef4251aa62a70cfa1bd6cf9ea9de02a6f3a2d77572a29a9f35991cae9b8
Tx public key: 337e13ad55da96608cf6f6e7fd5b2847e3424c8a952dd0a6a8093e2806f060aa
Timestamp: 1721957579 Timestamp [UCT]: 2024-07-26 01:32:59 Age [y:d:h:m:s]: 00:121:03:59:59
Block: 1073780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86696 RingCT/type: yes/0
Extra: 01337e13ad55da96608cf6f6e7fd5b2847e3424c8a952dd0a6a8093e2806f060aa021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de59e281d73e5e816e080c9bd51e48746c0209944c840be5baa7612005434820 0.600000000000 1546287 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": 1073790, "vin": [ { "gen": { "height": 1073780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de59e281d73e5e816e080c9bd51e48746c0209944c840be5baa7612005434820" } } ], "extra": [ 1, 51, 126, 19, 173, 85, 218, 150, 96, 140, 246, 246, 231, 253, 91, 40, 71, 227, 66, 76, 138, 149, 45, 208, 166, 168, 9, 62, 40, 6, 240, 96, 170, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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