Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fc659ced6ae35d41bd9f657de3fc022d5e6a1db9f7f8c99682a244ae1bdc3c5

Tx prefix hash: cde8735735f149193f46232808b614303eabca1b06e01a135c2d244ca43b6b11
Tx public key: 395ca134edbef61aac419d8925294c35701c085f078e8d8487e39aa1f0a34033
Timestamp: 1736525631 Timestamp [UCT]: 2025-01-10 16:13:51 Age [y:d:h:m:s]: 00:086:05:31:09
Block: 1194412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61404 RingCT/type: yes/0
Extra: 01395ca134edbef61aac419d8925294c35701c085f078e8d8487e39aa1f0a340330211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 339acf49cad9878b59379565e3e289fd4d1cb03dd8a193f323ec886f14d53544 0.600000000000 1680983 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": 1194422, "vin": [ { "gen": { "height": 1194412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "339acf49cad9878b59379565e3e289fd4d1cb03dd8a193f323ec886f14d53544" } } ], "extra": [ 1, 57, 92, 161, 52, 237, 190, 246, 26, 172, 65, 157, 137, 37, 41, 76, 53, 112, 28, 8, 95, 7, 142, 141, 132, 135, 227, 154, 161, 240, 163, 64, 51, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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