Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a26a0b85b45c29c122e3eb22ce45eecd381ce712879f4a5af296b479fc20c5a

Tx prefix hash: 6959f7aa1418f12761b76f133b09d55c9c54a8d3eecba982288ddba9f503dd69
Tx public key: bf5f097fb5f487824b3fab10152acf44a5bafbf6e9b65ea585dd69b8ee678d1c
Timestamp: 1701231340 Timestamp [UCT]: 2023-11-29 04:15:40 Age [y:d:h:m:s]: 01:087:00:22:21
Block: 901952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323308 RingCT/type: yes/0
Extra: 01bf5f097fb5f487824b3fab10152acf44a5bafbf6e9b65ea585dd69b8ee678d1c0211000000024b8f5122000000000000000000

1 output(s) for total of 0.630171251000 dcy

stealth address amount amount idx
00: 94ba225f9fd629ae1a9f58a059ce7e6bc83d986e7fca158e07d4cab4b5fb0b85 0.630171251000 1358551 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": 901962, "vin": [ { "gen": { "height": 901952 } } ], "vout": [ { "amount": 630171251, "target": { "key": "94ba225f9fd629ae1a9f58a059ce7e6bc83d986e7fca158e07d4cab4b5fb0b85" } } ], "extra": [ 1, 191, 95, 9, 127, 181, 244, 135, 130, 75, 63, 171, 16, 21, 42, 207, 68, 165, 186, 251, 246, 233, 182, 94, 165, 133, 221, 105, 184, 238, 103, 141, 28, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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