Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: faf8e5e759f763f78c05e0f30a7c305c96b940147f776bc93c35226be82b13bd

Tx prefix hash: 8b3a5863e69f6264e8ac4cd9a4847e164719314ed60801e3d65a70462fa0e3f8
Tx public key: c8645c52ac2d53ce50f639109fcd8694ab92d31b6f84e50d3c7fd1083340ad30
Timestamp: 1711737819 Timestamp [UCT]: 2024-03-29 18:43:39 Age [y:d:h:m:s]: 01:048:09:26:12
Block: 989076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295558 RingCT/type: yes/0
Extra: 01c8645c52ac2d53ce50f639109fcd8694ab92d31b6f84e50d3c7fd1083340ad3002110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a851ed60fbebdbc28c832e24ba06f28a2e799b728c845fd1049b07da3a14594 0.600000000000 1449371 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": 989086, "vin": [ { "gen": { "height": 989076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a851ed60fbebdbc28c832e24ba06f28a2e799b728c845fd1049b07da3a14594" } } ], "extra": [ 1, 200, 100, 92, 82, 172, 45, 83, 206, 80, 246, 57, 16, 159, 205, 134, 148, 171, 146, 211, 27, 111, 132, 229, 13, 60, 127, 209, 8, 51, 64, 173, 48, 2, 17, 0, 0, 0, 10, 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