Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e9dd7a4c33c5a24936d876192d33e1d5f0bfffd027191e54e409d9a51d62cbe

Tx prefix hash: 5c7e01a537eadd57a786a8662e7fce427ca9db5f3b70c27e18969eaba8cff02d
Tx public key: 4bcd19648f2d3a9e7960b6e099afb6816aea3d16d77f3e842f4206abd1b68dbf
Timestamp: 1727404797 Timestamp [UCT]: 2024-09-27 02:39:57 Age [y:d:h:m:s]: 00:195:04:57:13
Block: 1118944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139326 RingCT/type: yes/0
Extra: 014bcd19648f2d3a9e7960b6e099afb6816aea3d16d77f3e842f4206abd1b68dbf021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8d1736ab631f3741060583e966471a3aa28dae10cb12797656353403c20229b 0.600000000000 1600313 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": 1118954, "vin": [ { "gen": { "height": 1118944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8d1736ab631f3741060583e966471a3aa28dae10cb12797656353403c20229b" } } ], "extra": [ 1, 75, 205, 25, 100, 143, 45, 58, 158, 121, 96, 182, 224, 153, 175, 182, 129, 106, 234, 61, 22, 215, 127, 62, 132, 47, 66, 6, 171, 209, 182, 141, 191, 2, 17, 0, 0, 0, 7, 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