Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fc61217203f790cc0572398443f84a5d875d8738469292945bbf924e10b6776

Tx prefix hash: 01baa209ce45ea9130a1aace7f2a5d5a7431456602db75451a91128fb4f7bbb2
Tx public key: afa6cf96153835fa8d47e21aa1fb8fb156397039efe53aa1cc76089e25219f5c
Timestamp: 1746090302 Timestamp [UCT]: 2025-05-01 09:05:02 Age [y:d:h:m:s]: 00:198:17:23:08
Block: 1273325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139754 RingCT/type: yes/0
Extra: 01afa6cf96153835fa8d47e21aa1fb8fb156397039efe53aa1cc76089e25219f5c021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8f3b7e63b41b5a6efac86370191e1bf03221b759abb2dd599a664a1f11a8c0f 0.600000000000 1760606 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": 1273335, "vin": [ { "gen": { "height": 1273325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8f3b7e63b41b5a6efac86370191e1bf03221b759abb2dd599a664a1f11a8c0f" } } ], "extra": [ 1, 175, 166, 207, 150, 21, 56, 53, 250, 141, 71, 226, 26, 161, 251, 143, 177, 86, 57, 112, 57, 239, 229, 58, 161, 204, 118, 8, 158, 37, 33, 159, 92, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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