Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88a5daaf7f29be9ec91faafdefe74bbf4b988c3a27596660e77bcdc38cf6e1d2

Tx prefix hash: 283f19a5c955f9117d160b5ea55e7a1a4ee7328f9345771b4bf08a0d951fe199
Tx public key: de594db2486f880e82805b03f238fbd6e9ac2f02d51079badc282ea216b2f9de
Timestamp: 1706164042 Timestamp [UCT]: 2024-01-25 06:27:22 Age [y:d:h:m:s]: 01:091:03:58:25
Block: 942821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326272 RingCT/type: yes/0
Extra: 01de594db2486f880e82805b03f238fbd6e9ac2f02d51079badc282ea216b2f9de02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38caf2d9379c1b79a977f8494d869745dddf37dd1f0e12ab9d96daa8a5f87870 0.600000000000 1400999 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": 942831, "vin": [ { "gen": { "height": 942821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38caf2d9379c1b79a977f8494d869745dddf37dd1f0e12ab9d96daa8a5f87870" } } ], "extra": [ 1, 222, 89, 77, 178, 72, 111, 136, 14, 130, 128, 91, 3, 242, 56, 251, 214, 233, 172, 47, 2, 213, 16, 121, 186, 220, 40, 46, 162, 22, 178, 249, 222, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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