Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83d31882b544f418e5e99b0f33772320e1e3ad1c05fc2c58ca360f361baea828

Tx prefix hash: b319a42f71cf1eefd0aabd3dd8fb6bd3208396a4cf20422b5bf85cb3e0832e12
Tx public key: e9ef618d38252fe868f31db719777a44ec0da12a9d3e7dbf76e378b2f77d5c76
Timestamp: 1708894263 Timestamp [UCT]: 2024-02-25 20:51:03 Age [y:d:h:m:s]: 01:108:15:40:56
Block: 965487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0811 kB
Tx version: 2 No of confirmations: 338646 RingCT/type: yes/0
Extra: 01e9ef618d38252fe868f31db719777a44ec0da12a9d3e7dbf76e378b2f77d5c76

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b91c6b752eea3d7e7ea365a6981ae1ec092216e29a3f5303c04c79b0dc9a8f0e 0.600000000000 1425238 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": 965497, "vin": [ { "gen": { "height": 965487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b91c6b752eea3d7e7ea365a6981ae1ec092216e29a3f5303c04c79b0dc9a8f0e" } } ], "extra": [ 1, 233, 239, 97, 141, 56, 37, 47, 232, 104, 243, 29, 183, 25, 119, 122, 68, 236, 13, 161, 42, 157, 62, 125, 191, 118, 227, 120, 178, 247, 125, 92, 118 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8