Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48e7b96b8f9d8fc499cc4ec3dbe9ee2a89968c94382b401efef5ce91b2a6f621

Tx prefix hash: ece598c195768ae1a2c19a7127134ab4cf42524bea033ac036492afd6778aee1
Tx public key: 3bc11e44cf1ea5b5adf2f590a8e99a376e579843b0a4bbe4afb0b03a11f399c4
Timestamp: 1733090382 Timestamp [UCT]: 2024-12-01 21:59:42 Age [y:d:h:m:s]: 00:112:20:40:45
Block: 1165985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80451 RingCT/type: yes/0
Extra: 013bc11e44cf1ea5b5adf2f590a8e99a376e579843b0a4bbe4afb0b03a11f399c4021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fcd5b647566b5041c90d56c1776c08f0ce47b637a1924355f790bff9554c237 0.600000000000 1651662 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": 1165995, "vin": [ { "gen": { "height": 1165985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fcd5b647566b5041c90d56c1776c08f0ce47b637a1924355f790bff9554c237" } } ], "extra": [ 1, 59, 193, 30, 68, 207, 30, 165, 181, 173, 242, 245, 144, 168, 233, 154, 55, 110, 87, 152, 67, 176, 164, 187, 228, 175, 176, 176, 58, 17, 243, 153, 196, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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