Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9181d17d4fa3698fbe440d5a0044ee1933251fd3f39f59318b75db2774813297

Tx prefix hash: 44ffe3cdbb9edfbb2cedbd58fa1caaf26850f3a1d0285b83176a6096895730af
Tx public key: 5bbd2e56eae2092d2c4e2ca4a396e6c96442553bb3a1084a23a9f7abf6ddd97c
Timestamp: 1728079379 Timestamp [UCT]: 2024-10-04 22:02:59 Age [y:d:h:m:s]: 00:218:23:50:51
Block: 1124538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156331 RingCT/type: yes/0
Extra: 015bbd2e56eae2092d2c4e2ca4a396e6c96442553bb3a1084a23a9f7abf6ddd97c021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c44622310a8ef73f194cd6e29690169784363e47e26ccf0465d878a1b0584a2 0.600000000000 1607175 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": 1124548, "vin": [ { "gen": { "height": 1124538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c44622310a8ef73f194cd6e29690169784363e47e26ccf0465d878a1b0584a2" } } ], "extra": [ 1, 91, 189, 46, 86, 234, 226, 9, 45, 44, 78, 44, 164, 163, 150, 230, 201, 100, 66, 85, 59, 179, 161, 8, 74, 35, 169, 247, 171, 246, 221, 217, 124, 2, 17, 0, 0, 0, 1, 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