Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a6f6c894d999e8dafe97209aa6c19ec8cdaa64d9211c74de7ad6c02d84e204a

Tx prefix hash: 0c3e70755fad29a96d516719d78c69df344d61cb7e354a20b6d4d823f4be14e8
Tx public key: 9182dbb59cca638416da5e4113b0c6c845836d26e4170c719347c2a90d0935e1
Timestamp: 1643501684 Timestamp [UCT]: 2022-01-30 00:14:44 Age [y:d:h:m:s]: 03:083:17:32:21
Block: 428119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 839039 RingCT/type: yes/0
Extra: 019182dbb59cca638416da5e4113b0c6c845836d26e4170c719347c2a90d0935e10211000000012e6b1fd5000000000000000000

1 output(s) for total of 23.413392366000 dcy

stealth address amount amount idx
00: 4e4b969592fbfa76e2918d1f8b0ae50b214c4defb77256c4aab5983eac30fd55 23.413392366000 837435 of 0

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": 428129, "vin": [ { "gen": { "height": 428119 } } ], "vout": [ { "amount": 23413392366, "target": { "key": "4e4b969592fbfa76e2918d1f8b0ae50b214c4defb77256c4aab5983eac30fd55" } } ], "extra": [ 1, 145, 130, 219, 181, 156, 202, 99, 132, 22, 218, 94, 65, 19, 176, 198, 200, 69, 131, 109, 38, 228, 23, 12, 113, 147, 71, 194, 169, 13, 9, 53, 225, 2, 17, 0, 0, 0, 1, 46, 107, 31, 213, 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