Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 222e5f6dc9ba07b9211ed8d15c0ec98a7fd59974e16965233fc397a5dee559a8

Tx prefix hash: 2b95fe52c001c29695e11de32d0a1309deb4b768464e0fa96b1f63f1f5689cb5
Tx public key: 493402f77f42a5ce64e52d6b37efc134c7ea22dd65eab1549710a949e10c9c3c
Timestamp: 1721717054 Timestamp [UCT]: 2024-07-23 06:44:14 Age [y:d:h:m:s]: 00:261:22:08:53
Block: 1071780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187132 RingCT/type: yes/0
Extra: 01493402f77f42a5ce64e52d6b37efc134c7ea22dd65eab1549710a949e10c9c3c021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb38577a73e56d352dd19f554e56619d82fc2d3e56e5c0a65b547da9c1a129c0 0.600000000000 1544135 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": 1071790, "vin": [ { "gen": { "height": 1071780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb38577a73e56d352dd19f554e56619d82fc2d3e56e5c0a65b547da9c1a129c0" } } ], "extra": [ 1, 73, 52, 2, 247, 127, 66, 165, 206, 100, 229, 45, 107, 55, 239, 193, 52, 199, 234, 34, 221, 101, 234, 177, 84, 151, 16, 169, 73, 225, 12, 156, 60, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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