Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbaf60d3818b5b9b10d7e1e4120f0ea697ee31634c30ef78f81e9fbbfc06d7f4

Tx prefix hash: 22e3ae4b245d51132fdd3ebf1fdd7c11cf77d55e785cf22bb7aa773e4da44ee1
Tx public key: b8173b31e99bfbc22d74a20f7a708005233c974f078c1666e868033aee93f548
Timestamp: 1721178487 Timestamp [UCT]: 2024-07-17 01:08:07 Age [y:d:h:m:s]: 00:270:13:07:41
Block: 1067344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193271 RingCT/type: yes/0
Extra: 01b8173b31e99bfbc22d74a20f7a708005233c974f078c1666e868033aee93f548021100000014e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c7cc0b49661aa36e7fe766a622be8581ca0f3fdd3c32309d84c29bf409b5a39 0.600000000000 1538129 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": 1067354, "vin": [ { "gen": { "height": 1067344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c7cc0b49661aa36e7fe766a622be8581ca0f3fdd3c32309d84c29bf409b5a39" } } ], "extra": [ 1, 184, 23, 59, 49, 233, 155, 251, 194, 45, 116, 162, 15, 122, 112, 128, 5, 35, 60, 151, 79, 7, 140, 22, 102, 232, 104, 3, 58, 238, 147, 245, 72, 2, 17, 0, 0, 0, 20, 233, 20, 221, 21, 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