Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fccb8b1fd5289744f50a3e33b92899e0fb682ed15f71d939f55bec0bccdb3cd

Tx prefix hash: 714f5ae23c3c8ac224a1c7791b0368ec4a5945179b2cac1e85ef73342e5bd818
Tx public key: 0780f7f991892d48cea522987ff02f248cd9d1e78ad0f70391d071aba4f43024
Timestamp: 1745993075 Timestamp [UCT]: 2025-04-30 06:04:35 Age [y:d:h:m:s]: 00:204:18:21:50
Block: 1272542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144040 RingCT/type: yes/0
Extra: 010780f7f991892d48cea522987ff02f248cd9d1e78ad0f70391d071aba4f430240211000000069f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95b41733ae6a29d813479ad77146a6ee7c4fa83c0588afe23f3270fe824f41ef 0.600000000000 1759817 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": 1272552, "vin": [ { "gen": { "height": 1272542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95b41733ae6a29d813479ad77146a6ee7c4fa83c0588afe23f3270fe824f41ef" } } ], "extra": [ 1, 7, 128, 247, 249, 145, 137, 45, 72, 206, 165, 34, 152, 127, 240, 47, 36, 140, 217, 209, 231, 138, 208, 247, 3, 145, 208, 113, 171, 164, 244, 48, 36, 2, 17, 0, 0, 0, 6, 159, 159, 230, 140, 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