Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 361d3be2dc6751464e7653620317d6682065545d3b6b8869cebab95bc897f4d3

Tx prefix hash: 9d7eeb1c73a20ece6e51f4f9e8338864cc03c6ca17ea6b79c183cc2fcfd4a87f
Tx public key: 563e93383e53b24f06df032097ab042450b62621d9ccca515dc966f9cbda5f7b
Timestamp: 1696555158 Timestamp [UCT]: 2023-10-06 01:19:18 Age [y:d:h:m:s]: 01:186:21:10:49
Block: 863383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394612 RingCT/type: yes/0
Extra: 01563e93383e53b24f06df032097ab042450b62621d9ccca515dc966f9cbda5f7b021100000008faf35c9c000000000000000000

1 output(s) for total of 0.845772871000 dcy

stealth address amount amount idx
00: 610a87a28c781de459cd9b4dd6e29b8a9e1293ffb99a1b5e96f7ff191c0e8362 0.845772871000 1317835 of 0

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": 863393, "vin": [ { "gen": { "height": 863383 } } ], "vout": [ { "amount": 845772871, "target": { "key": "610a87a28c781de459cd9b4dd6e29b8a9e1293ffb99a1b5e96f7ff191c0e8362" } } ], "extra": [ 1, 86, 62, 147, 56, 62, 83, 178, 79, 6, 223, 3, 32, 151, 171, 4, 36, 80, 182, 38, 33, 217, 204, 202, 81, 93, 201, 102, 249, 203, 218, 95, 123, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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