Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a671adec1bae4a730850b1f7d8f9097801ac59f106486f260b5a442ab226a8b5

Tx prefix hash: 512f1e49465133395305dbecc45f62c4b044d4874faee3ac3881c88d74465c6f
Tx public key: cfc3cfc0aed86a4b7e2353af81aa5691f83f80377e3178dbc14e894246f13d75
Timestamp: 1756088810 Timestamp [UCT]: 2025-08-25 02:26:50 Age [y:d:h:m:s]: 00:088:13:29:35
Block: 1353828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63215 RingCT/type: yes/0
Extra: 01cfc3cfc0aed86a4b7e2353af81aa5691f83f80377e3178dbc14e894246f13d750211000000062609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e4aa5f8a46f3b5419a82893e1e42aaa5cab06fb515af6aa051103026f120ed2 0.600000000000 1841807 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": 1353838, "vin": [ { "gen": { "height": 1353828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e4aa5f8a46f3b5419a82893e1e42aaa5cab06fb515af6aa051103026f120ed2" } } ], "extra": [ 1, 207, 195, 207, 192, 174, 216, 106, 75, 126, 35, 83, 175, 129, 170, 86, 145, 248, 63, 128, 55, 126, 49, 120, 219, 193, 78, 137, 66, 70, 241, 61, 117, 2, 17, 0, 0, 0, 6, 38, 9, 179, 160, 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