Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2cbfc3757beb028b8e60cb4a363449faf82a7aa88bd6c28faec6f9ef9a56b6f

Tx prefix hash: bd0df28e2865e1d5f6bcded88a23b8eb780520073bf97256f1ef159fdf2f62d9
Tx public key: 475db2b2d98dd99a15db747b826c3c3754bd3dc1d111e041b7ad4185cfe87e8a
Timestamp: 1702757144 Timestamp [UCT]: 2023-12-16 20:05:44 Age [y:d:h:m:s]: 01:034:15:34:51
Block: 914607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286076 RingCT/type: yes/0
Extra: 01475db2b2d98dd99a15db747b826c3c3754bd3dc1d111e041b7ad4185cfe87e8a02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 643e777ee2d8389b72e3338c41a8f723e0f2a6b0dd60d538e4d1c4426d4207c9 0.600000000000 1371953 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": 914617, "vin": [ { "gen": { "height": 914607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "643e777ee2d8389b72e3338c41a8f723e0f2a6b0dd60d538e4d1c4426d4207c9" } } ], "extra": [ 1, 71, 93, 178, 178, 217, 141, 217, 154, 21, 219, 116, 123, 130, 108, 60, 55, 84, 189, 61, 193, 209, 17, 224, 65, 183, 173, 65, 133, 207, 232, 126, 138, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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