Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d0b12a9e48361b9eeb41f7778416c5f5253848f8d3901e7b4c61a68742cc0c5

Tx prefix hash: 5f2011b2ba1af0ec78808f848ab286667d42000a3e0ad8381d83139b52db9cda
Tx public key: ee6fe755e6e751f9f14a10c01070b567721d40938f7d773b8cb68bf435e75dde
Timestamp: 1736247718 Timestamp [UCT]: 2025-01-07 11:01:58 Age [y:d:h:m:s]: 00:297:08:28:59
Block: 1192117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210022 RingCT/type: yes/0
Extra: 01ee6fe755e6e751f9f14a10c01070b567721d40938f7d773b8cb68bf435e75dde021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 091fda05c967a6eb0d48ebdb8b1ccad9e33a6159d5f8d50a95eb8a3fa04b8262 0.600000000000 1678664 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": 1192127, "vin": [ { "gen": { "height": 1192117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "091fda05c967a6eb0d48ebdb8b1ccad9e33a6159d5f8d50a95eb8a3fa04b8262" } } ], "extra": [ 1, 238, 111, 231, 85, 230, 231, 81, 249, 241, 74, 16, 192, 16, 112, 181, 103, 114, 29, 64, 147, 143, 125, 119, 59, 140, 182, 139, 244, 53, 231, 93, 222, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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