Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5951e45e67437f5697411b58312335521bdb8f2cc0d4409ed96a920c54e134fa

Tx prefix hash: a07acc9904823dd7b53a4ef048a54c28385fbc13cd09a3ff06afe9c91619c2e7
Tx public key: 585ef54484c95f7c1d7ea8a312b343de24f693ba133e48c2b2a2858a1aff450e
Timestamp: 1708337432 Timestamp [UCT]: 2024-02-19 10:10:32 Age [y:d:h:m:s]: 01:027:02:40:49
Block: 960865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280418 RingCT/type: yes/0
Extra: 01585ef54484c95f7c1d7ea8a312b343de24f693ba133e48c2b2a2858a1aff450e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 553bf568be52b925dffb521409e75fa78cb2480560bf783ce19094b3aae5ecbe 0.600000000000 1420452 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": 960875, "vin": [ { "gen": { "height": 960865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "553bf568be52b925dffb521409e75fa78cb2480560bf783ce19094b3aae5ecbe" } } ], "extra": [ 1, 88, 94, 245, 68, 132, 201, 95, 124, 29, 126, 168, 163, 18, 179, 67, 222, 36, 246, 147, 186, 19, 62, 72, 194, 178, 162, 133, 138, 26, 255, 69, 14, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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