Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd3b28d439c74865b5a7f0e55b709991d91f6e90e6596045a57565ff633fd0d1

Tx prefix hash: 63019cc39391cca37a5024e3c73e805e1966d2e7ac2b4f3ab1da6aa397377456
Tx public key: b0a780eb2b09a6c9f11604b46f7d3cdf1f6b1a2f18058b4268d9e66abac20969
Timestamp: 1764726794 Timestamp [UCT]: 2025-12-03 01:53:14 Age [y:d:h:m:s]: 00:020:20:54:19
Block: 1425240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14924 RingCT/type: yes/0
Extra: 01b0a780eb2b09a6c9f11604b46f7d3cdf1f6b1a2f18058b4268d9e66abac20969021100000001defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7abe28f24fa4794adc0de436dbada27d3a72948efef4cee78d8421699a78dae0 0.600000000000 1913873 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": 1425250, "vin": [ { "gen": { "height": 1425240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7abe28f24fa4794adc0de436dbada27d3a72948efef4cee78d8421699a78dae0" } } ], "extra": [ 1, 176, 167, 128, 235, 43, 9, 166, 201, 241, 22, 4, 180, 111, 125, 60, 223, 31, 107, 26, 47, 24, 5, 139, 66, 104, 217, 230, 106, 186, 194, 9, 105, 2, 17, 0, 0, 0, 1, 222, 251, 143, 24, 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