Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5d28988f7b98cee65fdbefa902537e9caaed9eb8288714f3e7bda99abf85345

Tx prefix hash: b1cedb25a6b31e4436007de6cd6704d4fc5a06e3377a898be80fb0edd4d12b67
Tx public key: 3d3b0ba45d4f9e35ad51e81e0c16f2c9ca074bada055dce2ba6d253c24353ac3
Timestamp: 1722372006 Timestamp [UCT]: 2024-07-30 20:40:06 Age [y:d:h:m:s]: 01:100:09:54:16
Block: 1077213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330256 RingCT/type: yes/0
Extra: 013d3b0ba45d4f9e35ad51e81e0c16f2c9ca074bada055dce2ba6d253c24353ac3021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c53e99fd406cd09ef606bb398e09107475b5400ab32ceb54073c0dd6b1b865ea 0.600000000000 1549760 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": 1077223, "vin": [ { "gen": { "height": 1077213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c53e99fd406cd09ef606bb398e09107475b5400ab32ceb54073c0dd6b1b865ea" } } ], "extra": [ 1, 61, 59, 11, 164, 93, 79, 158, 53, 173, 81, 232, 30, 12, 22, 242, 201, 202, 7, 75, 173, 160, 85, 220, 226, 186, 109, 37, 60, 36, 53, 58, 195, 2, 17, 0, 0, 0, 3, 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