Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b04df3b8c689b6a8ab190bf1f284360008bab53afe5ac46d4609845ec0e190fe

Tx prefix hash: 3566062b54d23a1c01e30cc240438a0d7fc0875b1baa57719f899294aa2b9655
Tx public key: 30486d0040ca69e66fcda3852d573f801ecf4b6f6aa9712c23b7496e4de66b9d
Timestamp: 1710689191 Timestamp [UCT]: 2024-03-17 15:26:31 Age [y:d:h:m:s]: 01:073:00:58:13
Block: 980382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313216 RingCT/type: yes/0
Extra: 0130486d0040ca69e66fcda3852d573f801ecf4b6f6aa9712c23b7496e4de66b9d0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18263daa296ac043345f1af7b56022bcb8a2b8c2fb6c17047f387f761c4b5a42 0.600000000000 1440447 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": 980392, "vin": [ { "gen": { "height": 980382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18263daa296ac043345f1af7b56022bcb8a2b8c2fb6c17047f387f761c4b5a42" } } ], "extra": [ 1, 48, 72, 109, 0, 64, 202, 105, 230, 111, 205, 163, 133, 45, 87, 63, 128, 30, 207, 75, 111, 106, 169, 113, 44, 35, 183, 73, 110, 77, 230, 107, 157, 2, 17, 0, 0, 0, 8, 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