Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 385b24c1a822fc0c7b9a8f1aa08eb3e3509aba7ddc3fdd9aa94fc41729e08e51

Tx prefix hash: 9124c069cb8013284f8a6561a0a1e0c7dc59c6aa3cac7e90552196e32643298d
Tx public key: fcddff07fbd5f3248adecf296a55d201143101676bfe095137f4778a1675b3f0
Timestamp: 1697428603 Timestamp [UCT]: 2023-10-16 03:56:43 Age [y:d:h:m:s]: 01:189:22:38:12
Block: 870632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396777 RingCT/type: yes/0
Extra: 01fcddff07fbd5f3248adecf296a55d201143101676bfe095137f4778a1675b3f0021100000005faf35c9c000000000000000000

1 output(s) for total of 0.800266789000 dcy

stealth address amount amount idx
00: 9ce6796130c0dfb06fa3728c773ab867c3a5f6f111cfe06347dcd21b54534e83 0.800266789000 1325515 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": 870642, "vin": [ { "gen": { "height": 870632 } } ], "vout": [ { "amount": 800266789, "target": { "key": "9ce6796130c0dfb06fa3728c773ab867c3a5f6f111cfe06347dcd21b54534e83" } } ], "extra": [ 1, 252, 221, 255, 7, 251, 213, 243, 36, 138, 222, 207, 41, 106, 85, 210, 1, 20, 49, 1, 103, 107, 254, 9, 81, 55, 244, 119, 138, 22, 117, 179, 240, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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