Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 632d617f78533289896491b53cae875db55f166c67dca83b21ac2743da5bfeaa

Tx prefix hash: 46c09caf6a6e5918e1340911d4c92d912a708c501dddf563ef2ae077023e9549
Tx public key: 8aac7849291ac70daea270b2c409e6e58b749c5e375eea20c97ba6030ee44f49
Timestamp: 1752959864 Timestamp [UCT]: 2025-07-19 21:17:44 Age [y:d:h:m:s]: 00:114:03:26:06
Block: 1329079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80367 RingCT/type: yes/0
Extra: 018aac7849291ac70daea270b2c409e6e58b749c5e375eea20c97ba6030ee44f49021100000012bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e09d1fd058f4ed4f5ad2fbc0ce8f22a42f1a84fa05cc0c50ea37b6b0bd8207f 0.600000000000 1816854 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": 1329089, "vin": [ { "gen": { "height": 1329079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e09d1fd058f4ed4f5ad2fbc0ce8f22a42f1a84fa05cc0c50ea37b6b0bd8207f" } } ], "extra": [ 1, 138, 172, 120, 73, 41, 26, 199, 13, 174, 162, 112, 178, 196, 9, 230, 229, 139, 116, 156, 94, 55, 94, 234, 32, 201, 123, 166, 3, 14, 228, 79, 73, 2, 17, 0, 0, 0, 18, 191, 81, 178, 162, 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