Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 320658d5773d67d6f0f49746f291693ca82c91346e869b8f192bfa0f7556a0e9

Tx prefix hash: d94b9eaeba520b8fa9aad8802b42de2ead50e6ccc689c9ce564ed6abc04e8726
Tx public key: f17fc2abc359264430f9f029f68eb291e1770a5196e3075fe93f7b1a0ce56b59
Timestamp: 1704872213 Timestamp [UCT]: 2024-01-10 07:36:53 Age [y:d:h:m:s]: 01:136:07:37:07
Block: 932128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358571 RingCT/type: yes/0
Extra: 01f17fc2abc359264430f9f029f68eb291e1770a5196e3075fe93f7b1a0ce56b5902110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f88668067af6d59fe3a9f0692c97b292040bf7703d3f39930441339d8f0bc2ac 0.600000000000 1390050 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": 932138, "vin": [ { "gen": { "height": 932128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f88668067af6d59fe3a9f0692c97b292040bf7703d3f39930441339d8f0bc2ac" } } ], "extra": [ 1, 241, 127, 194, 171, 195, 89, 38, 68, 48, 249, 240, 41, 246, 142, 178, 145, 225, 119, 10, 81, 150, 227, 7, 95, 233, 63, 123, 26, 12, 229, 107, 89, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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