Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc42a884f3cb60d425fe8e290f876a30dd65cf8426c7a91f8ea389543d3a2b58

Tx prefix hash: 4183f606a4c5969c3cf385386cf7ddfd5bdc826b5510f7a18e956a99a636a322
Tx public key: 4ce57df03eab2420f48c7200cb84797a5d3a1f72e8d39cb2b339b30a764c3e65
Timestamp: 1707959494 Timestamp [UCT]: 2024-02-15 01:11:34 Age [y:d:h:m:s]: 00:274:02:00:53
Block: 957726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196235 RingCT/type: yes/0
Extra: 014ce57df03eab2420f48c7200cb84797a5d3a1f72e8d39cb2b339b30a764c3e6502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8e5d7bf1843f414ad42a3a7bb5550084dcb1c750de9e96e9477e5d6e34de685 0.600000000000 1417075 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": 957736, "vin": [ { "gen": { "height": 957726 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8e5d7bf1843f414ad42a3a7bb5550084dcb1c750de9e96e9477e5d6e34de685" } } ], "extra": [ 1, 76, 229, 125, 240, 62, 171, 36, 32, 244, 140, 114, 0, 203, 132, 121, 122, 93, 58, 31, 114, 232, 211, 156, 178, 179, 57, 179, 10, 118, 76, 62, 101, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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