Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e6cd97a5e2c5c681ef0bfb0c2e5ed4c6f0cd51f3b5ee37011a166db0536bf1a

Tx prefix hash: 5bc4fd05fd195826fd566ac45a74f382de4da2f94f3a3c84ae3280c2dbaff944
Tx public key: a3ae34fbe1c27f871b411a4f5d0373686998b140b070073c97d103cac77648bf
Timestamp: 1736564873 Timestamp [UCT]: 2025-01-11 03:07:53 Age [y:d:h:m:s]: 01:014:04:46:43
Block: 1194739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268434 RingCT/type: yes/0
Extra: 01a3ae34fbe1c27f871b411a4f5d0373686998b140b070073c97d103cac77648bf021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcbe905a8ca9172285fb379495417d15ed0f059424796e167349b82177ba1a7a 0.600000000000 1681316 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": 1194749, "vin": [ { "gen": { "height": 1194739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcbe905a8ca9172285fb379495417d15ed0f059424796e167349b82177ba1a7a" } } ], "extra": [ 1, 163, 174, 52, 251, 225, 194, 127, 135, 27, 65, 26, 79, 93, 3, 115, 104, 105, 152, 177, 64, 176, 112, 7, 60, 151, 209, 3, 202, 199, 118, 72, 191, 2, 17, 0, 0, 0, 3, 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