Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd7ea0ac32d4dccd6acabb77b317767b7bd61c4c30d23460ac469c2c89fb12bd

Tx prefix hash: 61a63664c0ba2f4e0e01301bdef8b6c6eea40b883d036f1122922b0b033dc6d8
Tx public key: 567572e8084a65fba8c95b08bac6894c3818856eda927e5d7e765759224a2b67
Timestamp: 1677446140 Timestamp [UCT]: 2023-02-26 21:15:40 Age [y:d:h:m:s]: 02:091:23:10:13
Block: 705646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 587358 RingCT/type: yes/0
Extra: 01567572e8084a65fba8c95b08bac6894c3818856eda927e5d7e765759224a2b6702110000000783600029000000000000000000

1 output(s) for total of 2.817745594000 dcy

stealth address amount amount idx
00: 9d58b8c7b83cf9c8a3c951115725c1f2b036904e0c680582ae282002c9fa078b 2.817745594000 1149353 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": 705656, "vin": [ { "gen": { "height": 705646 } } ], "vout": [ { "amount": 2817745594, "target": { "key": "9d58b8c7b83cf9c8a3c951115725c1f2b036904e0c680582ae282002c9fa078b" } } ], "extra": [ 1, 86, 117, 114, 232, 8, 74, 101, 251, 168, 201, 91, 8, 186, 198, 137, 76, 56, 24, 133, 110, 218, 146, 126, 93, 126, 118, 87, 89, 34, 74, 43, 103, 2, 17, 0, 0, 0, 7, 131, 96, 0, 41, 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