Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f09c5a4bab2d4d284f839365d0cbc902fc75b2594ab66a0b772f336e389ab467

Tx prefix hash: 8ee903fa096cec8c31c330a63b244eb41e5dbf283f02ba1e592821b2e577d9f7
Tx public key: b48b12b839c32241664c1aee2ec64794e89799c6cb16b9ed467a3baf7003e8cf
Timestamp: 1764672798 Timestamp [UCT]: 2025-12-02 10:53:18 Age [y:d:h:m:s]: 00:002:02:41:21
Block: 1424791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1524 RingCT/type: yes/0
Extra: 01b48b12b839c32241664c1aee2ec64794e89799c6cb16b9ed467a3baf7003e8cf021100000001da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a35d56eeeb6dfc0a80dcc1b87603a4ef2e8183f98dce4381bbe9f3e55ab61885 0.600000000000 1913422 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": 1424801, "vin": [ { "gen": { "height": 1424791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a35d56eeeb6dfc0a80dcc1b87603a4ef2e8183f98dce4381bbe9f3e55ab61885" } } ], "extra": [ 1, 180, 139, 18, 184, 57, 195, 34, 65, 102, 76, 26, 238, 46, 198, 71, 148, 232, 151, 153, 198, 203, 22, 185, 237, 70, 122, 59, 175, 112, 3, 232, 207, 2, 17, 0, 0, 0, 1, 218, 85, 72, 72, 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