Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be072a75635769b18f29a9a8556c5dff65406ecc87b4b2d9606e4069d137dd1c

Tx prefix hash: 7dc28cdc9ae40b931b511046fb9c6627a421ab0cb301006e332f28352cb45793
Tx public key: 8ad218db07a9f5500bc25f39177e7ca84c55d3f94c962790e4ff6d3cb9306456
Timestamp: 1710027424 Timestamp [UCT]: 2024-03-09 23:37:04 Age [y:d:h:m:s]: 01:026:20:45:35
Block: 974888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280179 RingCT/type: yes/0
Extra: 018ad218db07a9f5500bc25f39177e7ca84c55d3f94c962790e4ff6d3cb93064560211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1eeb8b058de13deb9f39072769b0d37e56ad9736509d5a4c56156b8708c3dbe 0.600000000000 1434855 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": 974898, "vin": [ { "gen": { "height": 974888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1eeb8b058de13deb9f39072769b0d37e56ad9736509d5a4c56156b8708c3dbe" } } ], "extra": [ 1, 138, 210, 24, 219, 7, 169, 245, 80, 11, 194, 95, 57, 23, 126, 124, 168, 76, 85, 211, 249, 76, 150, 39, 144, 228, 255, 109, 60, 185, 48, 100, 86, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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