Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 552e3ea42501bc7e5dbf693ca2ed56008f2b39b97cd391b05d5fb2f74034f493

Tx prefix hash: e6b74926aa3889dd4d205bfa1b51a07dec23d05b95d2a206a798bd2fec8f1fd3
Tx public key: c7289c49578af115c15b53e2a707f85a14a037c839613ca7d889f9d1d188cc62
Timestamp: 1705138588 Timestamp [UCT]: 2024-01-13 09:36:28 Age [y:d:h:m:s]: 00:363:22:08:43
Block: 934325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260560 RingCT/type: yes/0
Extra: 01c7289c49578af115c15b53e2a707f85a14a037c839613ca7d889f9d1d188cc6202110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bc38fd0e2dc0db42e2f5c472494785cd0e169cd663ea85b07e59b75e4a7fe0a 0.600000000000 1392325 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": 934335, "vin": [ { "gen": { "height": 934325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bc38fd0e2dc0db42e2f5c472494785cd0e169cd663ea85b07e59b75e4a7fe0a" } } ], "extra": [ 1, 199, 40, 156, 73, 87, 138, 241, 21, 193, 91, 83, 226, 167, 7, 248, 90, 20, 160, 55, 200, 57, 97, 60, 167, 216, 137, 249, 209, 209, 136, 204, 98, 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