Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c35206a04ee00f4f6963a0bf07816eb96ba4560e07e17f9a4e08806db038659

Tx prefix hash: 33724d1c22bb4effd6851549e3291655be0cb304b200e2ebc6e3ebfad32abc86
Tx public key: 38ccaa4a8cd9ba1d9ab88e6986ce7b025224aadcff25c9a23d4d5f1f1c1befc5
Timestamp: 1746205816 Timestamp [UCT]: 2025-05-02 17:10:16 Age [y:d:h:m:s]: 00:201:14:51:13
Block: 1274291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141816 RingCT/type: yes/0
Extra: 0138ccaa4a8cd9ba1d9ab88e6986ce7b025224aadcff25c9a23d4d5f1f1c1befc502110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08b28178eb1a0e9f236fcba40847ba6b0167e73edebeca2ebb2a6efc88e00b4f 0.600000000000 1761586 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": 1274301, "vin": [ { "gen": { "height": 1274291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08b28178eb1a0e9f236fcba40847ba6b0167e73edebeca2ebb2a6efc88e00b4f" } } ], "extra": [ 1, 56, 204, 170, 74, 140, 217, 186, 29, 154, 184, 142, 105, 134, 206, 123, 2, 82, 36, 170, 220, 255, 37, 201, 162, 61, 77, 95, 31, 28, 27, 239, 197, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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