Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9902cc719f59d3b4f41a7e4d4286730c39ae6c00fefa38d48feffb4de179d669

Tx prefix hash: 5c46e024ba7b9bbe615205dad1cc2c6b52013beedcaa5efd9538e94f2f1fada8
Tx public key: 80ff088416cb8561d15f31dddf699c903c51fb1a1a1ae31118fff58e677efe53
Timestamp: 1736527018 Timestamp [UCT]: 2025-01-10 16:36:58 Age [y:d:h:m:s]: 00:069:13:33:37
Block: 1194428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49508 RingCT/type: yes/0
Extra: 0180ff088416cb8561d15f31dddf699c903c51fb1a1a1ae31118fff58e677efe5302110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a8df128a62400f36da89a573b5d00f9d7e0a207d678aab5de44d1327c612bf3 0.600000000000 1680999 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": 1194438, "vin": [ { "gen": { "height": 1194428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a8df128a62400f36da89a573b5d00f9d7e0a207d678aab5de44d1327c612bf3" } } ], "extra": [ 1, 128, 255, 8, 132, 22, 203, 133, 97, 209, 95, 49, 221, 223, 105, 156, 144, 60, 81, 251, 26, 26, 26, 227, 17, 24, 255, 245, 142, 103, 126, 254, 83, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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