Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d41d7f1bd8cbeadcea59469d1f2b33734fa8e4c5faff0cf6de826c70b013fe31

Tx prefix hash: d35643ba03270741e96e954942d89164fe7130cb0b5fc2d1afb22565e8f9ce59
Tx public key: 595c53aaaf9f50aa0689ed42d5e7a364648b98f42282abb3c9702d225f0b8bc6
Timestamp: 1711623624 Timestamp [UCT]: 2024-03-28 11:00:24 Age [y:d:h:m:s]: 01:045:03:07:31
Block: 988124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293232 RingCT/type: yes/0
Extra: 01595c53aaaf9f50aa0689ed42d5e7a364648b98f42282abb3c9702d225f0b8bc602110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e3819a1a5686f756123478170b1a2c27774ac0fd82e90702592badac6dd14bb 0.600000000000 1448391 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": 988134, "vin": [ { "gen": { "height": 988124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e3819a1a5686f756123478170b1a2c27774ac0fd82e90702592badac6dd14bb" } } ], "extra": [ 1, 89, 92, 83, 170, 175, 159, 80, 170, 6, 137, 237, 66, 213, 231, 163, 100, 100, 139, 152, 244, 34, 130, 171, 179, 201, 112, 45, 34, 95, 11, 139, 198, 2, 17, 0, 0, 0, 8, 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