Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9118482cc18d3ea164f56ae8b59e906e6b5ba24aa20b73bfa90d66188583329

Tx prefix hash: cda1d248aeaf6393f880a82d0c92c0bbb8d3cfe5b258324ad2633486e82b3bbc
Tx public key: 5bed1c66491097a6523ae0806b5465b7c72e4a11b0e89068ba4d7d8bf1aee629
Timestamp: 1593018078 Timestamp [UCT]: 2020-06-24 17:01:18 Age [y:d:h:m:s]: 04:136:20:29:54
Block: 110518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1038034 RingCT/type: yes/0
Extra: 015bed1c66491097a6523ae0806b5465b7c72e4a11b0e89068ba4d7d8bf1aee62902110000001746a11e8a000000000000000000

1 output(s) for total of 264.124528679000 dcy

stealth address amount amount idx
00: c7c38c1529c6fa864871af6dc9c700c067cbe556cf9dd0e43bc42909b686b909 264.124528679000 191404 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": 110528, "vin": [ { "gen": { "height": 110518 } } ], "vout": [ { "amount": 264124528679, "target": { "key": "c7c38c1529c6fa864871af6dc9c700c067cbe556cf9dd0e43bc42909b686b909" } } ], "extra": [ 1, 91, 237, 28, 102, 73, 16, 151, 166, 82, 58, 224, 128, 107, 84, 101, 183, 199, 46, 74, 17, 176, 232, 144, 104, 186, 77, 125, 139, 241, 174, 230, 41, 2, 17, 0, 0, 0, 23, 70, 161, 30, 138, 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