Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e0973d13d76101c62a426776a1ed2e648b7d40f8f6653b25db4f90f44cc141c

Tx prefix hash: 88c815c238442e02d0ababcc30292fd283c2e9384fd49db56da4c39fe7bca5f2
Tx public key: 502bb9627813d7b73123d88ace0a4f96a4e00dfe00764df6118ca718e982f65b
Timestamp: 1734789939 Timestamp [UCT]: 2024-12-21 14:05:39 Age [y:d:h:m:s]: 00:000:16:37:49
Block: 1180077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498 RingCT/type: yes/0
Extra: 01502bb9627813d7b73123d88ace0a4f96a4e00dfe00764df6118ca718e982f65b021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d42a16a03ec912ae9e15c307d6cf7b94f0945fcc0e863182b31b99f3774a1e84 0.600000000000 1666482 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": 1180087, "vin": [ { "gen": { "height": 1180077 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d42a16a03ec912ae9e15c307d6cf7b94f0945fcc0e863182b31b99f3774a1e84" } } ], "extra": [ 1, 80, 43, 185, 98, 120, 19, 215, 183, 49, 35, 216, 138, 206, 10, 79, 150, 164, 224, 13, 254, 0, 118, 77, 246, 17, 140, 167, 24, 233, 130, 246, 91, 2, 17, 0, 0, 0, 9, 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