Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f7c25ff3b82c4d35f5794351572484fd616660e010daaaa4e4cbd436f09d741

Tx prefix hash: ffc6838ff13f17a91373a18cf9b7cea13d7c08793146c2ae6792aee6512b9e32
Tx public key: 030da696c17a23f04b3d831aa1447f58c14120bdeaaf09a1a2f01c14c0bb896e
Timestamp: 1749603384 Timestamp [UCT]: 2025-06-11 00:56:24 Age [y:d:h:m:s]: 00:161:13:18:27
Block: 1302418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113153 RingCT/type: yes/0
Extra: 01030da696c17a23f04b3d831aa1447f58c14120bdeaaf09a1a2f01c14c0bb896e021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f22f30d6367b1d5acd1a6305bfb31c3a97008ed19fd0b355f789d85894c1231 0.600000000000 1789989 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": 1302428, "vin": [ { "gen": { "height": 1302418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f22f30d6367b1d5acd1a6305bfb31c3a97008ed19fd0b355f789d85894c1231" } } ], "extra": [ 1, 3, 13, 166, 150, 193, 122, 35, 240, 75, 61, 131, 26, 161, 68, 127, 88, 193, 65, 32, 189, 234, 175, 9, 161, 162, 240, 28, 20, 192, 187, 137, 110, 2, 17, 0, 0, 0, 1, 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