Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f17a7830905be874b3846f577ad35c8298aced2f7bf71215b5d924c2b2f1bd3

Tx prefix hash: 3ee5a5274de7abea5d74526ffc399ad8dd32b4ff3872741e18e510e32dfdc816
Tx public key: f8172664acd3cbba02f7c8dab8d6a58da1e761285efda86197f531d5a1ef717c
Timestamp: 1724068556 Timestamp [UCT]: 2024-08-19 11:55:56 Age [y:d:h:m:s]: 01:094:07:19:28
Block: 1091289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325866 RingCT/type: yes/0
Extra: 01f8172664acd3cbba02f7c8dab8d6a58da1e761285efda86197f531d5a1ef717c02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e55b2647e063d103526aae6c82764df666e14d081fa7655837470af8329471d7 0.600000000000 1565920 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": 1091299, "vin": [ { "gen": { "height": 1091289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e55b2647e063d103526aae6c82764df666e14d081fa7655837470af8329471d7" } } ], "extra": [ 1, 248, 23, 38, 100, 172, 211, 203, 186, 2, 247, 200, 218, 184, 214, 165, 141, 161, 231, 97, 40, 94, 253, 168, 97, 151, 245, 49, 213, 161, 239, 113, 124, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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