Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0399f00aa0777afc41f4c794788346fe7c0e26f8ca1a0f2e0584d6043a33f42b

Tx prefix hash: efeed15c91bfefde75fb94e922d4e425588a95015829e50cbdc2826dd5edca33
Tx public key: e7c64c90c45e34788ec62c1c961939b9a82dbfcc7a7ac870e94b98b21d8d926c
Timestamp: 1751509023 Timestamp [UCT]: 2025-07-03 02:17:03 Age [y:d:h:m:s]: 00:174:00:44:30
Block: 1317630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122662 RingCT/type: yes/0
Extra: 01e7c64c90c45e34788ec62c1c961939b9a82dbfcc7a7ac870e94b98b21d8d926c0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f91267749b2d461695977da20608a401c7e8d95a06c4f7b0bf9185acd6c1888b 0.600000000000 1805299 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": 1317640, "vin": [ { "gen": { "height": 1317630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f91267749b2d461695977da20608a401c7e8d95a06c4f7b0bf9185acd6c1888b" } } ], "extra": [ 1, 231, 198, 76, 144, 196, 94, 52, 120, 142, 198, 44, 28, 150, 25, 57, 185, 168, 45, 191, 204, 122, 122, 200, 112, 233, 75, 152, 178, 29, 141, 146, 108, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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