Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5054d8d72994862a73b68c936c68f39ef72c552c4dc3eb2e2e418342ed10a1f

Tx prefix hash: a1421bfbdc72a771449a4a0a3cd4fd05f1c41997dbab176d620ef4daa291adb9
Tx public key: ac43b49e96a1f48df39d64b29f7987183ef203aa5f70fd6b300c7381fe1bbde8
Timestamp: 1700763050 Timestamp [UCT]: 2023-11-23 18:10:50 Age [y:d:h:m:s]: 01:151:23:23:53
Block: 898072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369790 RingCT/type: yes/0
Extra: 01ac43b49e96a1f48df39d64b29f7987183ef203aa5f70fd6b300c7381fe1bbde802110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.649104534000 dcy

stealth address amount amount idx
00: 2a108ac5f7b5bdc15929f780f7ccf9ae7d353957da6a7c7c3a3f1083276c96dc 0.649104534000 1354475 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": 898082, "vin": [ { "gen": { "height": 898072 } } ], "vout": [ { "amount": 649104534, "target": { "key": "2a108ac5f7b5bdc15929f780f7ccf9ae7d353957da6a7c7c3a3f1083276c96dc" } } ], "extra": [ 1, 172, 67, 180, 158, 150, 161, 244, 141, 243, 157, 100, 178, 159, 121, 135, 24, 62, 242, 3, 170, 95, 112, 253, 107, 48, 12, 115, 129, 254, 27, 189, 232, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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