Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c1c03cc0d79e5bd6ac9e817152b43f5dd2550cc23b12b38f9ac21eedf56858b

Tx prefix hash: 3f7da0367adb5d55fa6a57f81a9ce27faf9254b2ae0cf1ecb097f83fd143cae5
Tx public key: ad68d36b70966efb4b79422536befe87bcb017a667fd369486d800a8fe92844c
Timestamp: 1699606361 Timestamp [UCT]: 2023-11-10 08:52:41 Age [y:d:h:m:s]: 01:106:12:30:37
Block: 888488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337273 RingCT/type: yes/0
Extra: 01ad68d36b70966efb4b79422536befe87bcb017a667fd369486d800a8fe92844c02110000000333af99f4000000000000000000

1 output(s) for total of 0.698345642000 dcy

stealth address amount amount idx
00: 820ac1575034add8b87524a5e6d3f26e48a1b6ac80810c3a0fc00746cc097ea0 0.698345642000 1344431 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": 888498, "vin": [ { "gen": { "height": 888488 } } ], "vout": [ { "amount": 698345642, "target": { "key": "820ac1575034add8b87524a5e6d3f26e48a1b6ac80810c3a0fc00746cc097ea0" } } ], "extra": [ 1, 173, 104, 211, 107, 112, 150, 110, 251, 75, 121, 66, 37, 54, 190, 254, 135, 188, 176, 23, 166, 103, 253, 54, 148, 134, 216, 0, 168, 254, 146, 132, 76, 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