Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 998c7576e028102ca177a51e9d731e2b8d4f65749099e2aee40fbf52539996cd

Tx prefix hash: c72dc718b9a2f511dd7a641e100b175d85b4ea7d307d56b385a0fa45d6364d47
Tx public key: 29ade185f034d1bf69fafd91484f1d23d4097fd00ca522c36c5af58bc7cdf22d
Timestamp: 1733226068 Timestamp [UCT]: 2024-12-03 11:41:08 Age [y:d:h:m:s]: 00:116:00:57:28
Block: 1167106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82732 RingCT/type: yes/0
Extra: 0129ade185f034d1bf69fafd91484f1d23d4097fd00ca522c36c5af58bc7cdf22d0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31f9d42d4e23e95960cc791494a25cb8534093b50f7c3ff415e133b8a1243eee 0.600000000000 1652799 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": 1167116, "vin": [ { "gen": { "height": 1167106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31f9d42d4e23e95960cc791494a25cb8534093b50f7c3ff415e133b8a1243eee" } } ], "extra": [ 1, 41, 173, 225, 133, 240, 52, 209, 191, 105, 250, 253, 145, 72, 79, 29, 35, 212, 9, 127, 208, 12, 165, 34, 195, 108, 90, 245, 139, 199, 205, 242, 45, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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