Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57c68ca60d3cfb0cc1e5fd528f9563ee30435946fbc31081ba3a67e9ced7a9ed

Tx prefix hash: 84ab57fa4cd25e5aa72b6c5fab486fb7efef38ffad3083a4e9995f4817603dd2
Tx public key: eba25bf8eaa260aed005734d8eef3ebca5e298c5baa0c356773aa7c847a5a32c
Timestamp: 1745863501 Timestamp [UCT]: 2025-04-28 18:05:01 Age [y:d:h:m:s]: 00:010:05:29:16
Block: 1271469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7302 RingCT/type: yes/0
Extra: 01eba25bf8eaa260aed005734d8eef3ebca5e298c5baa0c356773aa7c847a5a32c0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bc6b0c2bb87840992a60e016b4531fe2c3f267242d501773a8b25612e0f8d99 0.600000000000 1758730 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": 1271479, "vin": [ { "gen": { "height": 1271469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bc6b0c2bb87840992a60e016b4531fe2c3f267242d501773a8b25612e0f8d99" } } ], "extra": [ 1, 235, 162, 91, 248, 234, 162, 96, 174, 208, 5, 115, 77, 142, 239, 62, 188, 165, 226, 152, 197, 186, 160, 195, 86, 119, 58, 167, 200, 71, 165, 163, 44, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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