Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1d7dc7f42e78f571732888dbae6bd438b0e5e0694df066bbe3843efd7fc8ec5

Tx prefix hash: d2ddde54725e74b9cc0bec6c6cc29e43a8056884e0796d8d5ae2ee1cce3ce567
Tx public key: 848305db41b5b389c598280d27d48bf910d48ad35d2a9ec7de8d513a0610933a
Timestamp: 1719403978 Timestamp [UCT]: 2024-06-26 12:12:58 Age [y:d:h:m:s]: 01:134:15:24:54
Block: 1052607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354775 RingCT/type: yes/0
Extra: 01848305db41b5b389c598280d27d48bf910d48ad35d2a9ec7de8d513a0610933a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b540f361078e51c7c9a21038a4f7a3d4f6ffe62edf6ce4fec88b337a7034cd52 0.600000000000 1522938 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": 1052617, "vin": [ { "gen": { "height": 1052607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b540f361078e51c7c9a21038a4f7a3d4f6ffe62edf6ce4fec88b337a7034cd52" } } ], "extra": [ 1, 132, 131, 5, 219, 65, 181, 179, 137, 197, 152, 40, 13, 39, 212, 139, 249, 16, 212, 138, 211, 93, 42, 158, 199, 222, 141, 81, 58, 6, 16, 147, 58, 2, 17, 0, 0, 0, 1, 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