Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ee1bb8baee4d632e0ad236d2fae1ea3b0ed3c590300092da45695cdecd16266

Tx prefix hash: 429869eea8d91b6e3116fcb0b4d67fe4d4bb1f40fc908bbe700335a88e54d12c
Tx public key: a98a1cd415f54b4dd776310251eabfdef29d2f741a97d962839ecd52c96d6546
Timestamp: 1707466672 Timestamp [UCT]: 2024-02-09 08:17:52 Age [y:d:h:m:s]: 00:342:04:54:04
Block: 953642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244984 RingCT/type: yes/0
Extra: 01a98a1cd415f54b4dd776310251eabfdef29d2f741a97d962839ecd52c96d654602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bca8164762590021f2a10cf52a88b3a85a7132c6e4b1eeec57bafea6574360b 0.600000000000 1412878 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": 953652, "vin": [ { "gen": { "height": 953642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bca8164762590021f2a10cf52a88b3a85a7132c6e4b1eeec57bafea6574360b" } } ], "extra": [ 1, 169, 138, 28, 212, 21, 245, 75, 77, 215, 118, 49, 2, 81, 234, 191, 222, 242, 157, 47, 116, 26, 151, 217, 98, 131, 158, 205, 82, 201, 109, 101, 70, 2, 17, 0, 0, 0, 1, 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