Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08c5eae7078e905851b66cc36487a46ee91e2fbd41d33a2a43c42c1a5bdb2bf9

Tx prefix hash: 5b94faf370c4863e28bd643fbeb23b1651a00d99cffcdeb8fac324e70c70e222
Tx public key: bbab464efc802d38352c667ca1f02d52fd29ab9b9be5f3ad2003b0ca7a5bb14b
Timestamp: 1733048384 Timestamp [UCT]: 2024-12-01 10:19:44 Age [y:d:h:m:s]: 00:111:01:24:00
Block: 1165643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79168 RingCT/type: yes/0
Extra: 01bbab464efc802d38352c667ca1f02d52fd29ab9b9be5f3ad2003b0ca7a5bb14b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb9a16a597341d69490a16d940571ab5dfd7b5fa6cc0d196c75824c36b4368df 0.600000000000 1651318 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": 1165653, "vin": [ { "gen": { "height": 1165643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb9a16a597341d69490a16d940571ab5dfd7b5fa6cc0d196c75824c36b4368df" } } ], "extra": [ 1, 187, 171, 70, 78, 252, 128, 45, 56, 53, 44, 102, 124, 161, 240, 45, 82, 253, 41, 171, 155, 155, 229, 243, 173, 32, 3, 176, 202, 122, 91, 177, 75, 2, 17, 0, 0, 0, 2, 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