Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c28e8dfd94813d9531eb5f537811c520a41cf971b64af75424e55f7e3228c028

Tx prefix hash: 675ee25aec4587546e6596e548641b52e9b2457d4fceb7094046016839ad06b5
Tx public key: d48add269e01b7bda06ad3d95509ab07e7108aa0365343c2c8e832f2e75438b2
Timestamp: 1700831826 Timestamp [UCT]: 2023-11-24 13:17:06 Age [y:d:h:m:s]: 01:163:06:48:54
Block: 898639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377882 RingCT/type: yes/0
Extra: 01d48add269e01b7bda06ad3d95509ab07e7108aa0365343c2c8e832f2e75438b202110000000c75e3f0e9000000000000000000

1 output(s) for total of 0.646302648000 dcy

stealth address amount amount idx
00: 94b94a7b934fec4350caafbd31d6b9cb4778c264eca9049376676f27816f37cd 0.646302648000 1355062 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": 898649, "vin": [ { "gen": { "height": 898639 } } ], "vout": [ { "amount": 646302648, "target": { "key": "94b94a7b934fec4350caafbd31d6b9cb4778c264eca9049376676f27816f37cd" } } ], "extra": [ 1, 212, 138, 221, 38, 158, 1, 183, 189, 160, 106, 211, 217, 85, 9, 171, 7, 231, 16, 138, 160, 54, 83, 67, 194, 200, 232, 50, 242, 231, 84, 56, 178, 2, 17, 0, 0, 0, 12, 117, 227, 240, 233, 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