Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42631f3331fe0b1ab9de03d88b100f1bde6e077e2a2912850e192efb59e57e6c

Tx prefix hash: 8aaa56789dcc22cfc3c6e7f5d03cb847a9100bbbb05deb481e5791fd997ad99d
Tx public key: aa8a5dfd02c492cae4645ca4bb60c6dcccbe1effdcb639debf0213930e20dff8
Timestamp: 1724813843 Timestamp [UCT]: 2024-08-28 02:57:23 Age [y:d:h:m:s]: 00:242:17:11:36
Block: 1097456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173350 RingCT/type: yes/0
Extra: 01aa8a5dfd02c492cae4645ca4bb60c6dcccbe1effdcb639debf0213930e20dff802110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90953a93784dcf007f12cdb06f0763e30ec3f9c0291d2d2293a3337fea36fe0c 0.600000000000 1572853 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": 1097466, "vin": [ { "gen": { "height": 1097456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90953a93784dcf007f12cdb06f0763e30ec3f9c0291d2d2293a3337fea36fe0c" } } ], "extra": [ 1, 170, 138, 93, 253, 2, 196, 146, 202, 228, 100, 92, 164, 187, 96, 198, 220, 204, 190, 30, 255, 220, 182, 57, 222, 191, 2, 19, 147, 14, 32, 223, 248, 2, 17, 0, 0, 0, 4, 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