Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c6c6e993a6b522096ad84308ad27eff47cf153ec5924f52d6456fd2be09077d

Tx prefix hash: d9660c8375d801744dfb4242f2bb8b6a7523c3b5838c07146fbb3c99a86d54d5
Tx public key: 9e623e9f949ab80b94727c9d0ccfca020ee1daeacbef9bd1a5bbdd86cc9995df
Timestamp: 1723516531 Timestamp [UCT]: 2024-08-13 02:35:31 Age [y:d:h:m:s]: 00:195:07:08:33
Block: 1086703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139430 RingCT/type: yes/0
Extra: 019e623e9f949ab80b94727c9d0ccfca020ee1daeacbef9bd1a5bbdd86cc9995df021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9403800a26b2ce2d68ee3a59d5cbd40ef9099b50234e012a36f2aa23549e911b 0.600000000000 1561302 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": 1086713, "vin": [ { "gen": { "height": 1086703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9403800a26b2ce2d68ee3a59d5cbd40ef9099b50234e012a36f2aa23549e911b" } } ], "extra": [ 1, 158, 98, 62, 159, 148, 154, 184, 11, 148, 114, 124, 157, 12, 207, 202, 2, 14, 225, 218, 234, 203, 239, 155, 209, 165, 187, 221, 134, 204, 153, 149, 223, 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