Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70ebda061ca3ed98364d680713e0fc155d4790fb666cefcd9618e585d5c0c655

Tx prefix hash: ca03b8e6ff1e0039ceb5b1dae990f81c8f24a9c3d295f3ced3638ea5ae811590
Tx public key: 71768feb8b420aa32032265212c092d12a2c9a0ec74ded7e66dd59f95af1ac5a
Timestamp: 1703711836 Timestamp [UCT]: 2023-12-27 21:17:16 Age [y:d:h:m:s]: 01:331:07:18:50
Block: 922517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495634 RingCT/type: yes/0
Extra: 0171768feb8b420aa32032265212c092d12a2c9a0ec74ded7e66dd59f95af1ac5a02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71a904f178fd5ce24e9ef2e4baaced24497db9cee70a29e35c2720a51db07e1a 0.600000000000 1380215 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": 922527, "vin": [ { "gen": { "height": 922517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71a904f178fd5ce24e9ef2e4baaced24497db9cee70a29e35c2720a51db07e1a" } } ], "extra": [ 1, 113, 118, 143, 235, 139, 66, 10, 163, 32, 50, 38, 82, 18, 192, 146, 209, 42, 44, 154, 14, 199, 77, 237, 126, 102, 221, 89, 249, 90, 241, 172, 90, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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