Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6df1a9e1a8691b653bf30a0177e3b89dc72c0f35367af49e3618bc400b9de776

Tx prefix hash: 428698d9988e52f9762f7d254f48402c1e775548f89838aa6fc7fd75f3c59108
Tx public key: 55d157f8a329feb1a1a1e83246e399ac1060e8be4cd7a17955961a694bff86e1
Timestamp: 1716530275 Timestamp [UCT]: 2024-05-24 05:57:55 Age [y:d:h:m:s]: 00:243:20:45:29
Block: 1028797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174476 RingCT/type: yes/0
Extra: 0155d157f8a329feb1a1a1e83246e399ac1060e8be4cd7a17955961a694bff86e10211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ec3f3d706a50be2c7696efe52bfff438588679ce83ce87bd98ef0f91c70f253 0.600000000000 1496794 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": 1028807, "vin": [ { "gen": { "height": 1028797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ec3f3d706a50be2c7696efe52bfff438588679ce83ce87bd98ef0f91c70f253" } } ], "extra": [ 1, 85, 209, 87, 248, 163, 41, 254, 177, 161, 161, 232, 50, 70, 227, 153, 172, 16, 96, 232, 190, 76, 215, 161, 121, 85, 150, 26, 105, 75, 255, 134, 225, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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