Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4138302e5268be18d21e6565c0a76aae0c1d7e28af2b68cef2b2c85ed734dda0

Tx prefix hash: 2b10ed3608f253388f76b887c7712c60f7926dfab3dd03f4529bab12f8e62693
Tx public key: 1aa785fdbd2a1403051868959a73e8e983a3dac16f32c39d84e62510b18869be
Timestamp: 1675162640 Timestamp [UCT]: 2023-01-31 10:57:20 Age [y:d:h:m:s]: 02:127:15:00:41
Block: 686702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 612892 RingCT/type: yes/0
Extra: 011aa785fdbd2a1403051868959a73e8e983a3dac16f32c39d84e62510b18869be0211000000015029cbac000000000000000000

1 output(s) for total of 3.255900641000 dcy

stealth address amount amount idx
00: a7f984d07917dd6897ccd736e6c4eb62df3d7a15d1cc8408c53ffcd48a66b5b1 3.255900641000 1129229 of 0

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": 686712, "vin": [ { "gen": { "height": 686702 } } ], "vout": [ { "amount": 3255900641, "target": { "key": "a7f984d07917dd6897ccd736e6c4eb62df3d7a15d1cc8408c53ffcd48a66b5b1" } } ], "extra": [ 1, 26, 167, 133, 253, 189, 42, 20, 3, 5, 24, 104, 149, 154, 115, 232, 233, 131, 163, 218, 193, 111, 50, 195, 157, 132, 230, 37, 16, 177, 136, 105, 190, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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