Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9571b5ff4a1941d39b5886b076497d3d59a8a766f2888761349a738b1b90274

Tx prefix hash: b20d0a3e22838c0bed0c3acd58cbf80d82ef99194cb03477e97e2e4b7ae578a7
Tx public key: 5f66158422cd5cd528206df2c40d4fac7b4c100e38dc0b40ccbf27762629224a
Timestamp: 1734994118 Timestamp [UCT]: 2024-12-23 22:48:38 Age [y:d:h:m:s]: 00:094:23:40:26
Block: 1181760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67654 RingCT/type: yes/0
Extra: 015f66158422cd5cd528206df2c40d4fac7b4c100e38dc0b40ccbf27762629224a021100000007d4a401e0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a7d7ba89592eb5e0276dc2412f150d6579ce0323144573b7c51a2af8fb69a1c 0.600000000000 1668185 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": 1181770, "vin": [ { "gen": { "height": 1181760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a7d7ba89592eb5e0276dc2412f150d6579ce0323144573b7c51a2af8fb69a1c" } } ], "extra": [ 1, 95, 102, 21, 132, 34, 205, 92, 213, 40, 32, 109, 242, 196, 13, 79, 172, 123, 76, 16, 14, 56, 220, 11, 64, 204, 191, 39, 118, 38, 41, 34, 74, 2, 17, 0, 0, 0, 7, 212, 164, 1, 224, 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