Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc53d09aff61104db9fd0cdd0035eb6730111feb82a59f220a2b3f2ef308e1e5

Tx prefix hash: 80ff2dabb383b9bcf373eb305172a5a7bde6cd24f13318c0c5d54c3bb01c41b2
Tx public key: 242f647c7a1e80f404eef83971974f577014a6675e9c1308ea8da1eb9d0f5de3
Timestamp: 1617509068 Timestamp [UCT]: 2021-04-04 04:04:28 Age [y:d:h:m:s]: 03:278:03:57:03
Block: 232848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 958479 RingCT/type: yes/0
Extra: 01242f647c7a1e80f404eef83971974f577014a6675e9c1308ea8da1eb9d0f5de30211000000207071732b000000000000000000

1 output(s) for total of 103.869006583000 dcy

stealth address amount amount idx
00: d3371a61beb2d2eba70d488e6b97a5b3a48aa87faf2a1ee3c0a8932f7f9fc94c 103.869006583000 483678 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": 232858, "vin": [ { "gen": { "height": 232848 } } ], "vout": [ { "amount": 103869006583, "target": { "key": "d3371a61beb2d2eba70d488e6b97a5b3a48aa87faf2a1ee3c0a8932f7f9fc94c" } } ], "extra": [ 1, 36, 47, 100, 124, 122, 30, 128, 244, 4, 238, 248, 57, 113, 151, 79, 87, 112, 20, 166, 103, 94, 156, 19, 8, 234, 141, 161, 235, 157, 15, 93, 227, 2, 17, 0, 0, 0, 32, 112, 113, 115, 43, 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