Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae9d88f6e11cf4ad2138817fc43e7fec47ee9fe871c775f3ac97b7f92b38ea50

Tx prefix hash: d2d98eb308b18841efe6859f8887f0fdce1f5d2e5ad0cc4636ac97793d64b7c0
Tx public key: c8479915c7d1a194bf0f72cd8e018c2f14bbef0181a728c5ff1581998ae51174
Timestamp: 1735993514 Timestamp [UCT]: 2025-01-04 12:25:14 Age [y:d:h:m:s]: 00:099:06:22:18
Block: 1190021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70732 RingCT/type: yes/0
Extra: 01c8479915c7d1a194bf0f72cd8e018c2f14bbef0181a728c5ff1581998ae511740211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96d8442ef98d2903e7e46e3b56a5d942ef5a00a82d4b25ba40a046533d14dec1 0.600000000000 1676536 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": 1190031, "vin": [ { "gen": { "height": 1190021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96d8442ef98d2903e7e46e3b56a5d942ef5a00a82d4b25ba40a046533d14dec1" } } ], "extra": [ 1, 200, 71, 153, 21, 199, 209, 161, 148, 191, 15, 114, 205, 142, 1, 140, 47, 20, 187, 239, 1, 129, 167, 40, 197, 255, 21, 129, 153, 138, 229, 17, 116, 2, 17, 0, 0, 0, 2, 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