Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee1be145c1f6e2a2c66ecce8873f09d81c3d33a4f07d1e9bf0a53b6edea6d01c

Tx prefix hash: efdf387696ac0efb5a086340d14dc0b6f2ddc8b8d24af24f8501e44bc3783ef9
Tx public key: 83b7c4b2244dcec06f0b36d5d18cbe0ce70525e446a6c21d5960d18ce9ea6758
Timestamp: 1725769928 Timestamp [UCT]: 2024-09-08 04:32:08 Age [y:d:h:m:s]: 00:212:07:46:29
Block: 1105398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151569 RingCT/type: yes/0
Extra: 0183b7c4b2244dcec06f0b36d5d18cbe0ce70525e446a6c21d5960d18ce9ea6758021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9751d1454309af47eba3ad1d9743ad4b27a505ce0d178cbe6346d6c625182d2 0.600000000000 1582741 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": 1105408, "vin": [ { "gen": { "height": 1105398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9751d1454309af47eba3ad1d9743ad4b27a505ce0d178cbe6346d6c625182d2" } } ], "extra": [ 1, 131, 183, 196, 178, 36, 77, 206, 192, 111, 11, 54, 213, 209, 140, 190, 12, 231, 5, 37, 228, 70, 166, 194, 29, 89, 96, 209, 140, 233, 234, 103, 88, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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