Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8a59a5ef76327a5daa7f8c2f4f2ec2c021b28936305134a86f85cb9fb1853ec

Tx prefix hash: 3f3437e9c5de42a8a61123d87de29d43936204cf238ab8ed61e3449791c9420d
Tx public key: 3642e6b23bf33be3ef803037fe05bac57bd19c764c3e106ee40e6c6c66d6e406
Timestamp: 1711433337 Timestamp [UCT]: 2024-03-26 06:08:57 Age [y:d:h:m:s]: 01:087:22:39:14
Block: 986552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323669 RingCT/type: yes/0
Extra: 013642e6b23bf33be3ef803037fe05bac57bd19c764c3e106ee40e6c6c66d6e40602110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f55cd4f14fbfb62b703a21ae7e71db31def72932ecdcbf57fd22f814c2bba1d4 0.600000000000 1446781 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": 986562, "vin": [ { "gen": { "height": 986552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f55cd4f14fbfb62b703a21ae7e71db31def72932ecdcbf57fd22f814c2bba1d4" } } ], "extra": [ 1, 54, 66, 230, 178, 59, 243, 59, 227, 239, 128, 48, 55, 254, 5, 186, 197, 123, 209, 156, 118, 76, 62, 16, 110, 228, 14, 108, 108, 102, 214, 228, 6, 2, 17, 0, 0, 0, 1, 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