Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ea736c219f363f2d6a45d4920496564ec0293e6ed683cc1f04815a4b8859b82

Tx prefix hash: 410eb87edf1bbde1201f0d8f7e6f46ddf50f7c11314daf1dc7101f52f8ae181d
Tx public key: b3a7c2821dc97a33c5780141bbf207960973c6c3979ae7bd990e12f81a5346b4
Timestamp: 1726638625 Timestamp [UCT]: 2024-09-18 05:50:25 Age [y:d:h:m:s]: 01:051:09:49:53
Block: 1112586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295155 RingCT/type: yes/0
Extra: 01b3a7c2821dc97a33c5780141bbf207960973c6c3979ae7bd990e12f81a5346b402110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da2b29d40a80f3fed47ae42daf6c60211f10ced63b671bd0be04b2ddad359429 0.600000000000 1591961 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": 1112596, "vin": [ { "gen": { "height": 1112586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da2b29d40a80f3fed47ae42daf6c60211f10ced63b671bd0be04b2ddad359429" } } ], "extra": [ 1, 179, 167, 194, 130, 29, 201, 122, 51, 197, 120, 1, 65, 187, 242, 7, 150, 9, 115, 198, 195, 151, 154, 231, 189, 153, 14, 18, 248, 26, 83, 70, 180, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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