Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d50c4f8f7b4315ea4ac8b223cf74a806917f507c16f94b9f58fa44eb17948490

Tx prefix hash: f541889ed6e85a5eb70fa917b3f91e89f52c94e6126849b51e84039c0a55b89f
Tx public key: 6810a6499f44ecbd023b41575f2cf2a6d301ccbbee6c64c70b3d9ce840ec5f49
Timestamp: 1734260781 Timestamp [UCT]: 2024-12-15 11:06:21 Age [y:d:h:m:s]: 00:330:15:54:27
Block: 1175694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233822 RingCT/type: yes/0
Extra: 016810a6499f44ecbd023b41575f2cf2a6d301ccbbee6c64c70b3d9ce840ec5f490211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47f4af206bab245e3420a4d5c87500b2affb3b696cd3ef33d8e102ec86623de0 0.600000000000 1662013 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": 1175704, "vin": [ { "gen": { "height": 1175694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47f4af206bab245e3420a4d5c87500b2affb3b696cd3ef33d8e102ec86623de0" } } ], "extra": [ 1, 104, 16, 166, 73, 159, 68, 236, 189, 2, 59, 65, 87, 95, 44, 242, 166, 211, 1, 204, 187, 238, 108, 100, 199, 11, 61, 156, 232, 64, 236, 95, 73, 2, 17, 0, 0, 0, 7, 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