Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e8b5aaee185131e00f77aef7f45980a6fcb7376ad062037289af6934598212d

Tx prefix hash: 1141af9b59603af0238864dda6802a3a2a20b3ebeda673dd2f6de7faaa8a9d60
Tx public key: 2fcb825bb759cc7798ea8c4b5c2cb9b62b55fee1f89a335603d68ca8c568b3a6
Timestamp: 1713320989 Timestamp [UCT]: 2024-04-17 02:29:49 Age [y:d:h:m:s]: 01:000:09:37:17
Block: 1002170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261240 RingCT/type: yes/0
Extra: 012fcb825bb759cc7798ea8c4b5c2cb9b62b55fee1f89a335603d68ca8c568b3a602110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0cf5641e1bc118150c49622981c50488e597a493551b8cbdb4727298189ca1d 0.600000000000 1462686 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": 1002180, "vin": [ { "gen": { "height": 1002170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0cf5641e1bc118150c49622981c50488e597a493551b8cbdb4727298189ca1d" } } ], "extra": [ 1, 47, 203, 130, 91, 183, 89, 204, 119, 152, 234, 140, 75, 92, 44, 185, 182, 43, 85, 254, 225, 248, 154, 51, 86, 3, 214, 140, 168, 197, 104, 179, 166, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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