Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53f4d0d452c2969220cb952c6107c74281c8c6eb91fb4e8e85d5fe7856f4022a

Tx prefix hash: a9f3c070f0a401be0a1af603fb2840b97a8a3c107dececf34ce1614564cb08b0
Tx public key: 8e9850fa8a420ef135fed5e8db7077cafd54ef897a81708b084d751728b58889
Timestamp: 1683691235 Timestamp [UCT]: 2023-05-10 04:00:35 Age [y:d:h:m:s]: 02:002:23:08:55
Block: 756788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524229 RingCT/type: yes/0
Extra: 018e9850fa8a420ef135fed5e8db7077cafd54ef897a81708b084d751728b5888902110000000333af99f4000000000000000000

1 output(s) for total of 1.907424653000 dcy

stealth address amount amount idx
00: fe17c59f142ef5de91796caaa520f839938a26436aba616d2c0ea7a4b0c335d7 1.907424653000 1205181 of 0

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": 756798, "vin": [ { "gen": { "height": 756788 } } ], "vout": [ { "amount": 1907424653, "target": { "key": "fe17c59f142ef5de91796caaa520f839938a26436aba616d2c0ea7a4b0c335d7" } } ], "extra": [ 1, 142, 152, 80, 250, 138, 66, 14, 241, 53, 254, 213, 232, 219, 112, 119, 202, 253, 84, 239, 137, 122, 129, 112, 139, 8, 77, 117, 23, 40, 181, 136, 137, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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