Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db6a387eb9071755d356050e8fce84ae87527475ebcd019c6ccae6e4aeed06ad

Tx prefix hash: fec58aa8202c8c71afa8749145e928df8c46b29efb8738596b058cda3c45ee78
Tx public key: 820cd18bbbf2dc20a83c33047819b5dc07c3b0a41c3e9116ade59a36bc0a3d0f
Timestamp: 1735361775 Timestamp [UCT]: 2024-12-28 04:56:15 Age [y:d:h:m:s]: 00:310:03:46:30
Block: 1184778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219170 RingCT/type: yes/0
Extra: 01820cd18bbbf2dc20a83c33047819b5dc07c3b0a41c3e9116ade59a36bc0a3d0f0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c82e1be5adaf4439a9036ee7ad8a02ecc2101a9bde855dbf03ca3923b8ad8d9f 0.600000000000 1671237 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": 1184788, "vin": [ { "gen": { "height": 1184778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c82e1be5adaf4439a9036ee7ad8a02ecc2101a9bde855dbf03ca3923b8ad8d9f" } } ], "extra": [ 1, 130, 12, 209, 139, 187, 242, 220, 32, 168, 60, 51, 4, 120, 25, 181, 220, 7, 195, 176, 164, 28, 62, 145, 22, 173, 229, 154, 54, 188, 10, 61, 15, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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