Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23e5e601ecd197727f0a33b2abfa73cc19881b9291c2a92ee8975b2e4ecb9e89

Tx prefix hash: d4f6360588fb4590b7cea1eb07d50063483de5f0a6e58017873f8af83bc0d0af
Tx public key: e50fbabb2d946e76b089ee519a6026b7bfefd2fd85dd38407acddf4abeb0fa1b
Timestamp: 1704273251 Timestamp [UCT]: 2024-01-03 09:14:11 Age [y:d:h:m:s]: 01:095:05:57:29
Block: 927174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329176 RingCT/type: yes/0
Extra: 01e50fbabb2d946e76b089ee519a6026b7bfefd2fd85dd38407acddf4abeb0fa1b02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c86b5f6cb614267fe4feec60fb3ea7a96dd6491f48ee2bcbd914af49ac40593f 0.600000000000 1384978 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": 927184, "vin": [ { "gen": { "height": 927174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c86b5f6cb614267fe4feec60fb3ea7a96dd6491f48ee2bcbd914af49ac40593f" } } ], "extra": [ 1, 229, 15, 186, 187, 45, 148, 110, 118, 176, 137, 238, 81, 154, 96, 38, 183, 191, 239, 210, 253, 133, 221, 56, 64, 122, 205, 223, 74, 190, 176, 250, 27, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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