Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02c8dd9841df8ddd17a78f5f9b7728e212dda52e770adeb236da5737320ed3ec

Tx prefix hash: de6151414aefc104628e10a55bdc3723c42a7882f7267c7c8bf51752da9e5cb5
Tx public key: 8a87c7c0993a75f6184509f2980892c38448b7244c6e8e7206a8195b7aacf5f4
Timestamp: 1733406209 Timestamp [UCT]: 2024-12-05 13:43:29 Age [y:d:h:m:s]: 00:101:15:19:26
Block: 1168599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72444 RingCT/type: yes/0
Extra: 018a87c7c0993a75f6184509f2980892c38448b7244c6e8e7206a8195b7aacf5f4021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abecddbf4634529ee072efb93a924ede96d67260c0101902e85d6d8f52c2be41 0.600000000000 1654310 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": 1168609, "vin": [ { "gen": { "height": 1168599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abecddbf4634529ee072efb93a924ede96d67260c0101902e85d6d8f52c2be41" } } ], "extra": [ 1, 138, 135, 199, 192, 153, 58, 117, 246, 24, 69, 9, 242, 152, 8, 146, 195, 132, 72, 183, 36, 76, 110, 142, 114, 6, 168, 25, 91, 122, 172, 245, 244, 2, 17, 0, 0, 0, 6, 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