Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffdbada2db065b048bcfb6ad16ee806e20feffe3e631b7a36ec6f8bf9cd8cfff

Tx prefix hash: bd29e230d803744a153aa8dfa9320e5c0c9912aa855dd102dc5972066eec2b40
Tx public key: 87aaee53ef4d7e62a01e7b8ecd493395fc9699ba7e61d1b335a49cad5fbf463d
Timestamp: 1724588327 Timestamp [UCT]: 2024-08-25 12:18:47 Age [y:d:h:m:s]: 00:245:09:51:44
Block: 1095593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175278 RingCT/type: yes/0
Extra: 0187aaee53ef4d7e62a01e7b8ecd493395fc9699ba7e61d1b335a49cad5fbf463d02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 171c8315afd8f3db6e4d8d844f778eb411cf95075510643726ccc4e08f6fbcb6 0.600000000000 1570774 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": 1095603, "vin": [ { "gen": { "height": 1095593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "171c8315afd8f3db6e4d8d844f778eb411cf95075510643726ccc4e08f6fbcb6" } } ], "extra": [ 1, 135, 170, 238, 83, 239, 77, 126, 98, 160, 30, 123, 142, 205, 73, 51, 149, 252, 150, 153, 186, 126, 97, 209, 179, 53, 164, 156, 173, 95, 191, 70, 61, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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