Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b69d65a7fd1b8a3be8ae296c77838bcd02ff4bda8a32403c3d0b5ce4273b51b7

Tx prefix hash: a13533157aafa314f09fa28244bec97a2f787f34baee915b3f88b40ec280b51c
Tx public key: ee5174ec5abac759154900221e8be7d7ca378e8e3d9708a61f8fe145ffd2720f
Timestamp: 1711269365 Timestamp [UCT]: 2024-03-24 08:36:05 Age [y:d:h:m:s]: 01:084:16:34:43
Block: 985196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321415 RingCT/type: yes/0
Extra: 01ee5174ec5abac759154900221e8be7d7ca378e8e3d9708a61f8fe145ffd2720f02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14d97598c2c873ee2d43917a1d4d628eb619f3dcd31332ea52e7b7c23c6d3b42 0.600000000000 1445405 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": 985206, "vin": [ { "gen": { "height": 985196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14d97598c2c873ee2d43917a1d4d628eb619f3dcd31332ea52e7b7c23c6d3b42" } } ], "extra": [ 1, 238, 81, 116, 236, 90, 186, 199, 89, 21, 73, 0, 34, 30, 139, 231, 215, 202, 55, 142, 142, 61, 151, 8, 166, 31, 143, 225, 69, 255, 210, 114, 15, 2, 17, 0, 0, 0, 2, 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