Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8ffe6f1f7758f5664b7369fae5bd06c13e2dca659915b6e829d421873ac0c89

Tx prefix hash: 57b1b991010edd0443dec50594e8d14095f6ec35b9d267b15191f1caede91099
Tx public key: dc91150546565a16fe0e4bfb9fcedb6cd52a9a9e99a5aff417a25bf07217c0c8
Timestamp: 1747025705 Timestamp [UCT]: 2025-05-12 04:55:05 Age [y:d:h:m:s]: 00:192:17:04:27
Block: 1281075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135443 RingCT/type: yes/0
Extra: 01dc91150546565a16fe0e4bfb9fcedb6cd52a9a9e99a5aff417a25bf07217c0c80211000000039f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 070f580457ce58c56e77d0a424b1cf9d3dad474f9c47906379ae260c5f5549d8 0.600000000000 1768470 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": 1281085, "vin": [ { "gen": { "height": 1281075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "070f580457ce58c56e77d0a424b1cf9d3dad474f9c47906379ae260c5f5549d8" } } ], "extra": [ 1, 220, 145, 21, 5, 70, 86, 90, 22, 254, 14, 75, 251, 159, 206, 219, 108, 213, 42, 154, 158, 153, 165, 175, 244, 23, 162, 91, 240, 114, 23, 192, 200, 2, 17, 0, 0, 0, 3, 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