Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 297e19b47e955ecc99738716603ed03e43f9ca304a009f2caf1250c500d5ac5a

Tx prefix hash: 864a518adcf08e25dc383f3a1679a16edef8bd7dea1a198212c819603c76b084
Tx public key: fa99ff458dfd39caaecec59f6d8e5689113a65f197d0096f2d928f41d2dd67f6
Timestamp: 1713860321 Timestamp [UCT]: 2024-04-23 08:18:41 Age [y:d:h:m:s]: 00:307:22:07:26
Block: 1006659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220087 RingCT/type: yes/0
Extra: 01fa99ff458dfd39caaecec59f6d8e5689113a65f197d0096f2d928f41d2dd67f60211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3dc9fdf55d86dc4b061c14d6bdb5b7c4ea22649af4115509b1253ab443df8682 0.600000000000 1467749 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": 1006669, "vin": [ { "gen": { "height": 1006659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3dc9fdf55d86dc4b061c14d6bdb5b7c4ea22649af4115509b1253ab443df8682" } } ], "extra": [ 1, 250, 153, 255, 69, 141, 253, 57, 202, 174, 206, 197, 159, 109, 142, 86, 137, 17, 58, 101, 241, 151, 208, 9, 111, 45, 146, 143, 65, 210, 221, 103, 246, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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