Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b233c4ca8350288a7072dc230368eb3295375e8843af799151eb1cd122c0e7c0

Tx prefix hash: 75ba9ec012c04215608490875f8f9dcb684d0d936a358362916453475abf18c3
Tx public key: 1d7d541ea1708b0ecf9d2bbd0f0ecbb1a34a5ddbf0d331f6c34673c0797d0c7d
Timestamp: 1733867035 Timestamp [UCT]: 2024-12-10 21:43:55 Age [y:d:h:m:s]: 00:107:16:39:44
Block: 1172422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76752 RingCT/type: yes/0
Extra: 011d7d541ea1708b0ecf9d2bbd0f0ecbb1a34a5ddbf0d331f6c34673c0797d0c7d021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ea4eee5691367119460e44484bd914d004c9145d2312c03126e438ff0084c00 0.600000000000 1658311 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": 1172432, "vin": [ { "gen": { "height": 1172422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ea4eee5691367119460e44484bd914d004c9145d2312c03126e438ff0084c00" } } ], "extra": [ 1, 29, 125, 84, 30, 161, 112, 139, 14, 207, 157, 43, 189, 15, 14, 203, 177, 163, 74, 93, 219, 240, 211, 49, 246, 195, 70, 115, 192, 121, 125, 12, 125, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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