Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5eaf2fc4ce56f8528efcbb2ca4696c274a7dbd9f9503e539cbd3df933f21402f

Tx prefix hash: b206736dae9c5124d3fd9d3d72d212aab4300c8cc87fed07146d2b9cc9f416b8
Tx public key: 3b00d60ead45a1f7c5719065d6f1db82337540ba731b61791309cb357f232090
Timestamp: 1746869645 Timestamp [UCT]: 2025-05-10 09:34:05 Age [y:d:h:m:s]: 00:257:06:26:04
Block: 1279782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181527 RingCT/type: yes/0
Extra: 013b00d60ead45a1f7c5719065d6f1db82337540ba731b61791309cb357f2320900211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc5822b3eeeaf585254d638c61412252fb5b7a94c8b86e0fea44989bf82b33c3 0.600000000000 1767163 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": 1279792, "vin": [ { "gen": { "height": 1279782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc5822b3eeeaf585254d638c61412252fb5b7a94c8b86e0fea44989bf82b33c3" } } ], "extra": [ 1, 59, 0, 214, 14, 173, 69, 161, 247, 197, 113, 144, 101, 214, 241, 219, 130, 51, 117, 64, 186, 115, 27, 97, 121, 19, 9, 203, 53, 127, 35, 32, 144, 2, 17, 0, 0, 0, 1, 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