Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a52f36ac0b212a077f57cce2a380bbed40b71a563b1feefa4a21c518aebf7a86

Tx prefix hash: e67d3b9bb823b55446cbf1e2b312a7952368ec98cf7bb5dd39718d0ef34ffdda
Tx public key: 88f5386ef211ab7bee0696e7bd0f7d0e7c86b1bcf8a0bc702bd65887054e3745
Timestamp: 1709090480 Timestamp [UCT]: 2024-02-28 03:21:20 Age [y:d:h:m:s]: 01:252:09:39:38
Block: 967117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439100 RingCT/type: yes/0
Extra: 0188f5386ef211ab7bee0696e7bd0f7d0e7c86b1bcf8a0bc702bd65887054e374502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f205a22ef31566a3dc4800daf55b64a718695637e6fddcc1d893d34d1bc60c45 0.600000000000 1426888 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": 967127, "vin": [ { "gen": { "height": 967117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f205a22ef31566a3dc4800daf55b64a718695637e6fddcc1d893d34d1bc60c45" } } ], "extra": [ 1, 136, 245, 56, 110, 242, 17, 171, 123, 238, 6, 150, 231, 189, 15, 125, 14, 124, 134, 177, 188, 248, 160, 188, 112, 43, 214, 88, 135, 5, 78, 55, 69, 2, 17, 0, 0, 0, 1, 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