Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e7856198fe0859a54f611dfcb9e02c6de0043a2896eb10f0df376121877ffe0

Tx prefix hash: 380dae09e1ba5cf410d8f87c39f169b78c44c2e6e97024081b5c39745cf3fa42
Tx public key: f61c46d0d5a66140b1be8f9ff2a6886edd8e4f17e756b05cfa0ae12853ba9eeb
Timestamp: 1738083914 Timestamp [UCT]: 2025-01-28 17:05:14 Age [y:d:h:m:s]: 01:004:20:45:52
Block: 1207069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262021 RingCT/type: yes/0
Extra: 01f61c46d0d5a66140b1be8f9ff2a6886edd8e4f17e756b05cfa0ae12853ba9eeb021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 570ebd1ca57c00e94507e131837d0c668b49e55c547a976b8c1a368368511b0d 0.600000000000 1693790 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": 1207079, "vin": [ { "gen": { "height": 1207069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "570ebd1ca57c00e94507e131837d0c668b49e55c547a976b8c1a368368511b0d" } } ], "extra": [ 1, 246, 28, 70, 208, 213, 166, 97, 64, 177, 190, 143, 159, 242, 166, 136, 110, 221, 142, 79, 23, 231, 86, 176, 92, 250, 10, 225, 40, 83, 186, 158, 235, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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